← previous blocknext block →recent activity
Analyzing
Block #106,950,693
15 transactions · 14 stateful · 2026-09-22 05:22:54 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,950,693 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w18w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c26d635…1bbf
0x34b655…2a6f
8 touches
6 conflicts
0x8590b692…b267
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xec1dd684…b6b3
0x34b655…2a6f
6 touches
3 conflicts
0xf67ba2c2…aa9c
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x681b1d0d…2e6b
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
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
6 conflicts on slot 0x6c26d63540…461bbf
Audit this contract →
← previous block·next block →recent activity