← previous blocknext block →recent activity
Analyzing
Block #83,632,709
15 transactions · 13 stateful · 2026-06-25 16:04:27 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,632,709 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w19w110w013w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23ab8481…52d5
0x34b655…2a6f
6 touches
3 conflicts
0x8a7af3fd…72a7
0x34b655…2a6f
4 touches
1 conflict
0xd653c5b0…a35a
0x34b655…2a6f
4 touches
1 conflict
0x6807402a…8631
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
0x34b655…2a6f
4 touches
1 conflict
0x619f5683…5bd4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
2 touches
0 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
3 conflicts on slot 0x23ab8481d2…ea52d5
Audit this contract →
← previous block·next block →recent activity