← previous blocknext block →recent activity
Analyzing
Block #83,617,611
14 transactions · 12 stateful · 2026-06-25 14:23:32 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,617,611 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w08w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd06d821c…e5d0
0x34b655…2a6f
8 touches
6 conflicts
0x3c9bce0e…0440
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x872e51c8…ae28
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00966e54…7d1d
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 0xd06d821c57…9fe5d0
Audit this contract →
← previous block·next block →recent activity