← previous blocknext block →recent activity
Analyzing
Block #106,046,137
16 transactions · 15 stateful · 2026-09-19 01:29:15 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,046,137 · 16 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
1w02w08w09w110w113w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1a79e9de…99e6
0x851145…3f07
4 touches
1 conflict
0xc73fd549…2e28
0x851145…3f07
4 touches
1 conflict
0x1aa3d799…a59e
0x6f6493…b480
3 touches
1 conflict
0x1aa3d799…a5a2
0x6f6493…b480
3 touches
1 conflict
0x1dd8a04d…f8d8
0x6f6493…b480
3 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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity