← previous blocknext block →recent activity
Analyzing
Block #91,411,569
13 transactions · 12 stateful · 2026-07-29 18:09:50 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,411,569 · 13 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
1w02w03w14w16w08w09w110w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724cd9ff…6684
0x0cc9b2…7777
6 touches
3 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
6 touches
3 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
6 touches
3 conflicts
0x00000000…0008
0x0ea966…0742
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0000
0x614b85…a284
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)
3 conflicts on slot 0x724cd9ff19…4c6684
Audit this contract →
← previous block·next block →recent activity