← previous blocknext block →recent activity
Analyzing
Block #106,539,445
18 transactions · 16 stateful · 2026-09-20 18:52:02 UTC
Parallelism
83/100
Blocked
19%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,539,445 · 18 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
2w09w010w114w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16a8cd0c…27bd
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xc52785b9…08f8
0x34b655…2a6f
4 touches
1 conflict
0xf7343b2c…7543
0x34b655…2a6f
4 touches
1 conflict
0xb0e8e2d9…121d
0x34b655…2a6f
3 touches
1 conflict
0x7b6d2deb…dde0
0x34b655…2a6f
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
3 conflicts on slot 0x16a8cd0cae…8827bd
Audit this contract →
← previous block·next block →recent activity