← previous blocknext block →recent activity
Analyzing
Block #83,624,369
22 transactions · 19 stateful · 2026-06-25 15:08:45 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,624,369 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w28w09w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xaa7ee7…f0e4
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xaa6f28d9…83ef
0x34b655…2a6f
4 touches
2 conflicts
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x9fbabe09…8dd6
0x34b655…2a6f
4 touches
1 conflict
0xbbec4dcb…832e
0x34b655…2a6f
4 touches
1 conflict
0xc73022f6…c813
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: 0xaa7ee7ce…aff0e4
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity