← previous blocknext block →recent activity
Analyzing
Block #92,698,215
18 transactions · 18 stateful · 2026-08-03 06:03:24 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,698,215 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w38w09w110w211w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724cd9ff…6684
0x0cc9b2…7777
14 touches
21 conflicts
0x00000000…0008
0x0ea966…0742
14 touches
21 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
14 touches
21 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb1
0x1b6862…e19c
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)
21 conflicts on slot 0x724cd9ff19…4c6684
Audit this contract →
← previous block·next block →recent activity