← previous blocknext block →recent activity
Analyzing
Block #84,575,766
19 transactions · 19 stateful · 2026-06-30 00:51:26 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,575,766 · 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
2w03w14w25w36w47w58w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xabd0fca8…b1d4
0x34b655…2a6f
4 touches
1 conflict
0xea2644f5…8c97
0x34b655…2a6f
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
2 touches
0 conflicts
0x67e17ebe…a709
0x065c9d…c394
2 touches
0 conflicts
0x9a2199a4…7084
0x065c9d…c394
2 touches
0 conflicts
0xbd87d610…6da7
0x065c9d…c394
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: 0xd637b38f…c64160
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity