← previous blocknext block →recent activity
Analyzing
Block #83,628,934
19 transactions · 18 stateful · 2026-06-25 15:39:14 UTC
Parallelism
84/100
Blocked
22%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,628,934 · 19 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
4w05w16w07w08w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xe02484a6…c32e
0xc8689a…ee79
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xfd5ef2cf…02ae
0x34b655…2a6f
4 touches
1 conflict
0x31dde271…109c
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x37a276a3…673f
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
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
1 conflict on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity