← previous blocknext block →recent activity
Analyzing
Block #84,176,180
14 transactions · 12 stateful · 2026-06-28 04:27:25 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,176,180 · 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
4w05w06w17w211w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8372997…869e
0x34b655…2a6f
6 touches
3 conflicts
0xb9593682…3806
0x754704…b603
6 touches
3 conflicts
0xd0031975…cbe2
0x754704…b603
6 touches
3 conflicts
0xb147eeb0…d658
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8d37ba41…71f2
0x34b655…2a6f
4 touches
1 conflict
0xa16b3e4e…0786
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
3 conflicts on slot 0xf8372997e5…13869e
Audit this contract →
← previous block·next block →recent activity