← previous blocknext block →recent activity
Analyzing
Block #84,352,405
12 transactions · 10 stateful · 2026-06-29 00:01:38 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,352,405 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w16w07w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb983f9fc…9b91
0xdde003…c9a4
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0xbfe63d66…c3e6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0016
0x8fbe07…71b6
4 touches
1 conflict
0x0494780e…2900
0x8fbe07…71b6
4 touches
1 conflict
0xa6fd7409…16b7
0x8fbe07…71b6
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5ebb19ec…ce9a
0xdde003…c9a4
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: 0xdde00377…29c9a4
1 conflict on slot 0xb983f9fc1c…ab9b91
Audit this contract →
← previous block·next block →recent activity