← previous blocknext block →recent activity
Analyzing
Block #83,654,123
12 transactions · 9 stateful · 2026-06-25 18:27:27 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,654,123 · 12 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
2w03w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xc9fe0433…7f01
0x34b655…2a6f
6 touches
3 conflicts
0x73ca2093…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x1f4116cf…a89e
0x34b655…2a6f
4 touches
1 conflict
0x3f17ba84…aa87
0x34b655…2a6f
4 touches
1 conflict
0x40f51104…c272
0x34b655…2a6f
4 touches
1 conflict
0x68159d45…c1ac
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity