← previous blocknext block →recent activity
Analyzing
Block #83,957,027
23 transactions · 20 stateful · 2026-06-27 04:07:49 UTC
Parallelism
87/100
Blocked
35%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,957,027 · 23 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
2w03w14w06w17w29w011w112w013w116w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x00966e54…7d1d
0x34b655…2a6f
4 touches
1 conflict
0x0708f4d7…8354
0x34b655…2a6f
4 touches
1 conflict
0x0ee9bf3f…0dac
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x29210375…f851
0x34b655…2a6f
4 touches
1 conflict
0x6b47245e…a342
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: 0xd637b38f…c64160
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity