← previous blocknext block →recent activity
Analyzing
Block #106,224,192
21 transactions · 21 stateful · 2026-09-19 16:25:23 UTC
Parallelism
90/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,224,192 · 21 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w010w113w014w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9ad2151…0c8d
0x34b655…2a6f
4 touches
1 conflict
0xef8e1fb3…23ac
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x8488f10f…9353
0x34ae4d…3fc5
2 touches
0 conflicts
0x8488f10f…9354
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 0xd9ad215176…ad0c8d
Audit this contract →
← previous block·next block →recent activity