← previous blocknext block →recent activity
Analyzing
Block #102,251,568
19 transactions · 19 stateful · 2026-09-05 18:06:57 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,251,568 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w010w111w213w214w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1997ab0…3b2e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x5da92df7…74b5
0x34b655…2a6f
6 touches
3 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0xf195ad96…e0c3
0x34b655…2a6f
4 touches
1 conflict
0x08399ab6…0057
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xe1997ab090…493b2e
Audit this contract →
← previous block·next block →recent activity