← previous blocknext block →recent activity
Analyzing
Block #84,117,176
13 transactions · 11 stateful · 2026-06-27 21:54:45 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,117,176 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w09w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d0b5783…2cf4
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xb577a4a7…a670
0x34b655…2a6f
4 touches
1 conflict
0xd5d0a749…c426
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0005
0x663d48…5149
4 touches
1 conflict
0x706796c2…d491
0x754704…b603
4 touches
1 conflict
0x5d7f309d…5145
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 0x1d0b5783f3…b52cf4
Audit this contract →
← previous block·next block →recent activity