← previous blocknext block →recent activity
Analyzing
Block #105,626,207
13 transactions · 13 stateful · 2026-09-17 14:13:16 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,626,207 · 13 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
1w02w14w05w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05b9a9e9…43e6
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x1a99f155…77b7
0x34b655…2a6f
4 touches
1 conflict
0x1a9aeb78…0a0e
0x34b655…2a6f
4 touches
1 conflict
0x2d0d2d5e…1634
0x34b655…2a6f
4 touches
1 conflict
0x3f25409b…f92b
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x58c3dacf…cb15
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 0x05b9a9e960…3343e6
Audit this contract →
← previous block·next block →recent activity