← previous blocknext block →recent activity
Analyzing
Block #105,643,392
27 transactions · 23 stateful · 2026-09-17 15:39:47 UTC
Parallelism
74/100
Blocked
52%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,643,392 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w09w110w220w625w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88e92ec7…696d
0x34b655…2a6f
14 touches
21 conflicts
0xa023938c…de9d
0x34b655…2a6f
12 touches
15 conflicts
0xf346808d…6ad4
0x34b655…2a6f
8 touches
6 conflicts
0xa8590d68…d5c8
0x34b655…2a6f
8 touches
6 conflicts
0xe343c220…9393
0x34b655…2a6f
6 touches
3 conflicts
0x5c7b5ec0…0764
0x34b655…2a6f
6 touches
3 conflicts
0x2aa7be4c…0f84
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
21 conflicts on slot 0x88e92ec750…6f696d
Audit this contract →
← previous block·next block →recent activity