← previous blocknext block →recent activity
Analyzing
Block #106,186,312
19 transactions · 14 stateful · 2026-09-19 13:14:42 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,186,312 · 19 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
1w02w06w110w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x3643741b…109c
0x34b655…2a6f
4 touches
1 conflict
0x366a19b0…f065
0x34b655…2a6f
4 touches
1 conflict
0x3f152ba8…cea6
0x34b655…2a6f
4 touches
1 conflict
0x577e9a2a…3561
0x34b655…2a6f
4 touches
1 conflict
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0x6dfae6fe…a6f1
0x34b655…2a6f
4 touches
1 conflict
0x766c0128…5cb9
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: Kuru Exchange: MarginAccount
1 conflict on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity