← previous blocknext block →recent activity
Analyzing
Block #100,604,937
43 transactions · 24 stateful · 2026-08-30 23:48:31 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.72
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,604,937 · 43 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w010w112w013w214w315w416w518w020w636w138w139w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xdfa159d0…1576
0x065c9d…c394
10 touches
10 conflicts
0xbb97db90…4c93
0xc8689a…ee79
8 touches
6 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0x06e40499…165e
0x2b46c0…1669
8 touches
6 conflicts
0xa605468c…1bfc
0x2b46c0…1669
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: Market-MON/USDC
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity