← previous blocknext block →recent activity
Analyzing
Block #96,191,955
16 transactions · 16 stateful · 2026-08-15 11:30:16 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,191,955 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w17w08w19w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724cd9ff…6684
0x0cc9b2…7777
12 touches
15 conflicts
0x00000000…0008
0x0ea966…0742
12 touches
15 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
12 touches
15 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x78860c4f…cade
0x34b655…2a6f
4 touches
1 conflict
0x376c9634…97d2
0x34b655…2a6f
2 touches
0 conflicts
0x3f57bd36…7796
0x34b655…2a6f
2 touches
0 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: MONI (MONI)
15 conflicts on slot 0x724cd9ff19…4c6684
Audit this contract →
← previous block·next block →recent activity