← previous blocknext block →recent activity
Analyzing
Block #98,575,911
16 transactions · 16 stateful · 2026-08-23 20:51:21 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,575,911 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w19w211w012w113w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724cd9ff…6684
0x0cc9b2…7777
6 touches
3 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
6 touches
3 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
6 touches
3 conflicts
0x00000000…0008
0x0ea966…0742
6 touches
3 conflicts
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x2cc76c10…81a5
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: MONI (MONI)
3 conflicts on slot 0x724cd9ff19…4c6684
Audit this contract →
← previous block·next block →recent activity