← previous blocknext block →recent activity
Analyzing
Block #106,042,964
50 transactions · 29 stateful · 2026-09-19 01:13:17 UTC
Parallelism
78/100
Blocked
52%
Avg conflicts / tx
0.96
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,042,964 · 50 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w113w215w016w317w426w527w633w741w144w948w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
16 touches
28 conflicts
0x4d22a4ef…e47f
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xcc8faac2…c766
0x065c9d…c394
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xbcea3008…27bf
0x065c9d…c394
7 touches
6 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0x06e40499…165e
0x34ae4d…3fc5
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
28 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity