← previous blocknext block →recent activity
Analyzing
Block #106,329,623
34 transactions · 24 stateful · 2026-09-20 01:15:59 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,329,623 · 34 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
4w05w16w27w38w018w421w022w124w227w129w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x18cf3003…51d1
0x065c9d…c394
8 touches
6 conflicts
0xcc8faac2…c766
0x065c9d…c394
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0x06e40499…165e
0x34ae4d…3fc5
8 touches
6 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
8 touches
6 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
8 touches
6 conflicts
0x65903ef9…2567
0x34b655…2a6f
8 touches
6 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: Kuru Exchange: MarginAccount
10 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity