← previous blocknext block →recent activity
Analyzing
Block #106,017,771
17 transactions · 17 stateful · 2026-09-18 23:06:30 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,017,771 · 17 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
1w02w04w16w07w112w213w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8359dce…7328
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x735a86cd…b64d
0x34b655…2a6f
4 touches
1 conflict
0xdb067026…9eb8
0x34ae4d…3fc5
2 touches
0 conflicts
0xe2263bea…6a9e
0x34ae4d…3fc5
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
1 conflict on slot 0xa8359dceed…bb7328
Audit this contract →
← previous block·next block →recent activity