← previous blocknext block →recent activity
Analyzing
Block #105,633,663
25 transactions · 23 stateful · 2026-09-17 14:50:48 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,633,663 · 25 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
2w03w16w07w111w012w113w014w115w117w018w121w022w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b1d04b9…fa60
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xc4d98fb1…c354
0x40c49f…2af0
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x11d5aca2…a990
0x34b655…2a6f
4 touches
1 conflict
0x55be8fdb…b46d
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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
3 conflicts on slot 0x5b1d04b905…b8fa60
Audit this contract →
← previous block·next block →recent activity