← previous blocknext block →recent activity
Analyzing
Block #84,576,392
17 transactions · 16 stateful · 2026-06-30 00:55:36 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,576,392 · 17 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
2w06w07w19w113w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea2644f5…8c97
0x34b655…2a6f
8 touches
6 conflicts
0xabd0fca8…b1d4
0x34b655…2a6f
6 touches
3 conflicts
0x07a45c06…5f8d
0x34b655…2a6f
4 touches
1 conflict
0x0edfa9f5…0a84
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x274b85f7…c526
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity