← previous blocknext block →recent activity
Analyzing
Block #83,452,281
17 transactions · 15 stateful · 2026-06-24 20:00:31 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,452,281 · 17 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
1w02w03w16w07w110w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ad4d28a…c788
0x34b655…2a6f
6 touches
3 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
4 touches
1 conflict
0x6a15f784…10b2
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x508644a7…d54e
0x40c49f…2af0
3 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
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
3 conflicts on slot 0x9ad4d28af1…c2c788
Audit this contract →
← previous block·next block →recent activity