← previous blocknext block →recent activity
Analyzing
Block #102,284,429
21 transactions · 20 stateful · 2026-09-05 20:53:35 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,284,429 · 21 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
1w02w14w05w06w17w011w112w213w214w315w416w517w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8dd89a73…c067
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x4dffc33e…068d
0x34b655…2a6f
4 touches
1 conflict
0x5212b133…97bb
0x34b655…2a6f
4 touches
1 conflict
0x738d841d…3c29
0x34b655…2a6f
4 touches
1 conflict
0x79ec4509…1f61
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 0x8dd89a730c…04c067
Audit this contract →
← previous block·next block →recent activity