← previous blocknext block →recent activity
Analyzing
Block #83,642,172
8 transactions · 6 stateful · 2026-06-25 17:07:40 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,642,172 · 8 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
1w02w15w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda5e0705…ecb9
0x34b655…2a6f
6 touches
3 conflicts
0xffb1ee54…7c2c
0x34b655…2a6f
6 touches
3 conflicts
0x9de92e44…acf4
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
2 touches
0 conflicts
0x6bcfbf05…c7fe
0x34b655…2a6f
2 touches
0 conflicts
0x7e6c970a…65af
0x34b655…2a6f
2 touches
0 conflicts
0x7fe97198…79ab
0x34b655…2a6f
2 touches
0 conflicts
0x845d95c8…db0f
0x34b655…2a6f
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 0xda5e0705c4…a5ecb9
Audit this contract →
← previous block·next block →recent activity