← previous blocknext block →recent activity
Analyzing
Block #83,937,245
24 transactions · 18 stateful · 2026-06-27 01:55:59 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,937,245 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w26w37w18w216w218w222w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac33ff75…077b
0xfa32f9…f3f0
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 conflicts
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0xd95b1a11…4e4d
0x754704…b603
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: 0xfa32f9ec…fef3f0
3 conflicts on slot 0xac33ff75c1…89077b
Audit this contract →
← previous block·next block →recent activity