← previous blocknext block →recent activity
Analyzing
Block #83,453,443
39 transactions · 26 stateful · 2026-06-24 20:08:18 UTC
Parallelism
87/100
Blocked
35%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,453,443 · 39 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
5w07w012w114w115w025w126w227w028w333w034w135w236w337w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x834eed09…3ace
0xd32edf…ff58
7 touches
6 conflicts
0x6713b018…05f3
0x34b655…2a6f
6 touches
3 conflicts
0x08ec900c…20e6
0x34b655…2a6f
6 touches
3 conflicts
0x7a2b18bf…d24e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x52687386…26ce
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity