← previous blocknext block →recent activity
Analyzing
Block #102,282,817
16 transactions · 16 stateful · 2026-09-05 20:45:25 UTC
Parallelism
63/100
Blocked
31%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,282,817 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w211w313w014w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe108b282…58b3
0x34b655…2a6f
4 touches
1 conflict
0x81a7ba4d…8c4b
0x23c26b…7777
2 touches
0 conflicts
0x01555e5f…b666
0x34b655…2a6f
2 touches
0 conflicts
0x1a3d2527…8ca0
0x34b655…2a6f
2 touches
0 conflicts
0x5da59c2b…d7b2
0x34b655…2a6f
2 touches
0 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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity