← previous blocknext block →recent activity
Analyzing
Block #84,524,468
16 transactions · 13 stateful · 2026-06-29 19:08:53 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,524,468 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w18w010w111w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff2b017…3fa2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x300bc9e7…7ed2
0x34b655…2a6f
4 touches
1 conflict
0x305e6edb…89b1
0x34b655…2a6f
4 touches
1 conflict
0x67d8b378…f2f8
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
3 conflicts on slot 0x9ff2b0179a…1c3fa2
Audit this contract →
← previous block·next block →recent activity