← previous blocknext block →recent activity
Analyzing
Block #84,292,407
16 transactions · 16 stateful · 2026-06-28 17:21:51 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,292,407 · 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
1w02w18w09w210w311w414w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9db7b4d…2957
0x40c49f…2af0
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x6d02ef01…fe34
0x40c49f…2af0
2 touches
0 conflicts
0x74447d5e…9fe0
0x40c49f…2af0
2 touches
0 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
2 touches
0 conflicts
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: 0x40c49f17…d22af0
3 conflicts on slot 0xa9db7b4dd0…562957
Audit this contract →
← previous block·next block →recent activity