← previous blocknext block →recent activity
Analyzing
Block #102,019,761
14 transactions · 14 stateful · 2026-09-04 22:32:03 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,019,761 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f17174f…68b4
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd4f6a526…ad10
0x34b655…2a6f
4 touches
1 conflict
0xdec2aeb2…0586
0x34b655…2a6f
4 touches
1 conflict
0xee46716c…d788
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
1 conflict on slot 0x2f17174f4c…6568b4
Audit this contract →
← previous block·next block →recent activity