← previous blocknext block →recent activity
Analyzing
Block #83,853,372
22 transactions · 20 stateful · 2026-06-26 16:36:51 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,853,372 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w611w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0xf6884b1c…8b7f
0x34b655…2a6f
3 touches
1 conflict
0x2fe9992f…4143
0x34b655…2a6f
3 touches
1 conflict
0xcd9a9bc6…b25f
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
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity