← previous blocknext block →recent activity
Analyzing
Block #106,342,160
16 transactions · 15 stateful · 2026-09-20 02:19:05 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,342,160 · 16 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
2w03w04w05w17w010w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbac938a…d380
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1a99f155…77b7
0x34b655…2a6f
4 touches
1 conflict
0x20d42b37…52c9
0x34b655…2a6f
4 touches
1 conflict
0x25eb7079…cb76
0x34b655…2a6f
4 touches
1 conflict
0x38faf16c…0987
0x34b655…2a6f
4 touches
1 conflict
0x6d59a973…32a9
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 0xdbac938a0b…21d380
Audit this contract →
← previous block·next block →recent activity