← previous blocknext block →recent activity
Analyzing
Block #105,760,139
32 transactions · 26 stateful · 2026-09-18 01:27:22 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,760,139 · 32 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
1w03w15w08w09w111w114w015w121w224w127w228w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0xddc0d3c8…6039
0x065c9d…c394
6 touches
3 conflicts
0xb0cbcced…df5c
0x99c7a7…8bf0
4 touches
1 conflict
0x5c67c8a0…e6f3
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity