← previous blocknext block →recent activity
Analyzing
Block #106,955,925
23 transactions · 18 stateful · 2026-09-22 05:49:14 UTC
Parallelism
78/100
Blocked
56%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,955,925 · 23 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
1w02w13w24w35w06w17w213w014w118w420w221w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb87af72a…aef6
0x2a68ba…90c5
10 touches
10 conflicts
0x6fddef5c…eedd
0x065c9d…c394
7 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
4 touches
1 conflict
0x4d828f7b…296f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x71ecf7c5…8b1e
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
10 conflicts on slot 0xb87af72ae5…0baef6
Audit this contract →
← previous block·next block →recent activity