← previous blocknext block →recent activity
Analyzing
Block #83,479,937
15 transactions · 13 stateful · 2026-06-24 23:05:10 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,479,937 · 15 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
2w03w15w06w18w09w111w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7fe05cd…207e
0x34b655…2a6f
6 touches
3 conflicts
0x2d1b334d…c1ba
0x34b655…2a6f
6 touches
3 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
6 touches
3 conflicts
0x126a0344…4465
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2ea7b6bb…7e5c
0x34b655…2a6f
4 touches
1 conflict
0x4abf223d…0915
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
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 0xd7fe05cdfa…d0207e
Audit this contract →
← previous block·next block →recent activity