← previous blocknext block →recent activity
Analyzing
Block #84,318,346
19 transactions · 18 stateful · 2026-06-28 20:14:37 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,318,346 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w09w010w111w112w213w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc5f346…7b42
0x40c49f…2af0
6 touches
3 conflicts
0x5da4ed2f…283f
0xa6afd3…d132
4 touches
1 conflict
0x1b3f23da…7b77
0x34b655…2a6f
4 touches
1 conflict
0x2d5dedaa…2fa6
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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: 0x40c49f17…d22af0
3 conflicts on slot 0xdfc5f34630…0b7b42
Audit this contract →
← previous block·next block →recent activity