← previous blocknext block →recent activity
Analyzing
Block #84,355,487
30 transactions · 19 stateful · 2026-06-29 00:22:12 UTC
Parallelism
87/100
Blocked
37%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,355,487 · 30 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
3w015w016w117w218w320w023w124w226w028w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x37a276a3…673f
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
6 touches
3 conflicts
0x75194ada…a1c5
0x34b655…2a6f
6 touches
3 conflicts
0x1222e42d…7dc8
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity