← previous blocknext block →recent activity
Analyzing
Block #83,493,230
11 transactions · 9 stateful · 2026-06-25 00:33:45 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,493,230 · 11 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
4w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05289bd6…9ab4
0x34b655…2a6f
4 touches
1 conflict
0x6159d117…2e7e
0x34b655…2a6f
4 touches
1 conflict
0xb6acec9c…ea53
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x5b09d694…26a2
0x40c49f…2af0
2 touches
0 conflicts
0xc03d5696…b11f
0x40c49f…2af0
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: Perpl
1 conflict on slot 0x05289bd631…b49ab4
Audit this contract →
← previous block·next block →recent activity