← previous blocknext block →recent activity
Analyzing
Block #91,008,183
11 transactions · 11 stateful · 2026-07-28 08:18:53 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,008,183 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x759e9124…1381
0x065c9d…c394
2 touches
0 conflicts
0x9f8d9271…fdcf
0x065c9d…c394
2 touches
0 conflicts
0xe84aeeb2…bdf6
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0070
0x1efe02…37d6
2 touches
0 conflicts
0x2bd31d9a…1c22
0x1efe02…37d6
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity