← previous blocknext block →recent activity
Analyzing
Block #84,571,267
16 transactions · 13 stateful · 2026-06-30 00:21:27 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,571,267 · 16 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
4w05w06w18w29w010w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7e2f1b7…7e6f
0x34b655…2a6f
6 touches
3 conflicts
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x8fa9d65b…0e4b
0x34b655…2a6f
4 touches
1 conflict
0x5bdb0bbb…f5a2
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x05a7428b…ddf3
0x34b655…2a6f
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
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
3 conflicts on slot 0xa7e2f1b7f5…cf7e6f
Audit this contract →
← previous block·next block →recent activity