← previous blocknext block →recent activity
Analyzing
Block #83,639,873
18 transactions · 16 stateful · 2026-06-25 16:52:19 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,639,873 · 18 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
1w02w13w04w16w08w19w215w116w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda5e0705…ecb9
0x34b655…2a6f
8 touches
6 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
6 touches
3 conflicts
0xffb1ee54…7c2c
0x34b655…2a6f
6 touches
3 conflicts
0x7e6c970a…65af
0x34b655…2a6f
4 touches
1 conflict
0x972e0369…65f5
0x34b655…2a6f
4 touches
1 conflict
0x9b58e20f…2dd9
0x34b655…2a6f
4 touches
1 conflict
0x9fc02c82…7403
0x34b655…2a6f
4 touches
1 conflict
0xbfe63d66…c3e6
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 0xda5e0705c4…a5ecb9
Audit this contract →
← previous block·next block →recent activity