← previous blocknext block →recent activity
Analyzing
Block #84,411,130
14 transactions · 12 stateful · 2026-06-29 06:33:06 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,411,130 · 14 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
1w02w13w14w29w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x2f7781d6…e632
0x34b655…2a6f
6 touches
3 conflicts
0x00d87b1e…ac16
0x34b655…2a6f
6 touches
3 conflicts
0x454d8940…cfe7
0x34b655…2a6f
4 touches
1 conflict
0x4a14d167…0226
0x34b655…2a6f
4 touches
1 conflict
0x55384053…4a1f
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity