← previous blocknext block →recent activity
Analyzing
Block #84,352,930
24 transactions · 20 stateful · 2026-06-29 00:05:09 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,352,930 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w07w08w111w012w113w215w316w119w220w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6d4eb00…30f3
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xf57b32fa…1ec6
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x08d1b814…125d
0x34b655…2a6f
4 touches
1 conflict
0x12403b0a…a8ab
0x34b655…2a6f
4 touches
1 conflict
0x454d8940…cfe7
0x34b655…2a6f
4 touches
1 conflict
0x75cdffd8…c217
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 0xd6d4eb00b3…a430f3
Audit this contract →
← previous block·next block →recent activity