← previous blocknext block →recent activity
Analyzing
Block #83,668,738
19 transactions · 18 stateful · 2026-06-25 20:04:52 UTC
Parallelism
63/100
Blocked
39%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,668,738 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w38w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb670a63e…ead8
0x34b655…2a6f
12 touches
15 conflicts
0xaa198c38…7b0a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xde696e46…6446
0x34b655…2a6f
6 touches
3 conflicts
0x3e505a15…70f8
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0xa560feae…f13f
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xb670a63ebd…04ead8
Audit this contract →
← previous block·next block →recent activity