← previous blocknext block →recent activity
Analyzing
Block #84,118,486
19 transactions · 17 stateful · 2026-06-27 22:03:32 UTC
Parallelism
68/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,118,486 · 19 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
3w05w18w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x019ded9d…6fa0
0x34b655…2a6f
6 touches
3 conflicts
0xc983cab3…daa5
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
0x2f7f1a44…eeeb
0x34b655…2a6f
4 touches
1 conflict
0x38ec2c24…ef42
0x34b655…2a6f
4 touches
1 conflict
0x3e505a15…70f8
0x34b655…2a6f
4 touches
1 conflict
0x3ea509ec…d963
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 0x019ded9dc2…f06fa0
Audit this contract →
← previous block·next block →recent activity