← previous blocknext block →recent activity
Analyzing
Block #83,665,057
20 transactions · 17 stateful · 2026-06-25 19:40:16 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,665,057 · 20 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
1w02w14w05w18w29w312w413w014w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec71d7fa…def3
0x34b655…2a6f
10 touches
10 conflicts
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0xe64e6363…e676
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xec71d7fa9a…01def3
Audit this contract →
← previous block·next block →recent activity