← previous blocknext block →recent activity
Analyzing
Block #83,631,784
18 transactions · 18 stateful · 2026-06-25 15:58:16 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,631,784 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w413w015w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82dd2252…e1ce
0x34b655…2a6f
10 touches
10 conflicts
0xd08b8a31…0998
0x34b655…2a6f
10 touches
10 conflicts
0x5396d712…a139
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x3ec82b22…1f46
0x34b655…2a6f
6 touches
3 conflicts
0x94dc8af7…ec26
0x34b655…2a6f
6 touches
3 conflicts
0x75d24ace…e359
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
10 conflicts on slot 0x82dd22520c…26e1ce
Audit this contract →
← previous block·next block →recent activity