← previous blocknext block →recent activity
Analyzing
Block #83,410,294
20 transactions · 18 stateful · 2026-06-24 15:20:05 UTC
Parallelism
85/100
Blocked
28%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,410,294 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w08w110w014w117w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x124be23b…2cca
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb99958f6…ccf0
0x34b655…2a6f
4 touches
1 conflict
0xb99958f6…ccf1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xde1c4907…a810
0x34b655…2a6f
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
3 conflicts on slot 0x124be23b2d…3b2cca
Audit this contract →
← previous block·next block →recent activity