← previous blocknext block →recent activity
Analyzing
Block #94,486,465
20 transactions · 19 stateful · 2026-08-09 12:14:31 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,486,465 · 20 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
2w03w14w28w09w110w211w312w413w514w616w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79b05f7b…32da
0x065c9d…c394
14 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
14 touches
21 conflicts
0x0778475b…bd75
0x2a68ba…90c5
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x921a58d1…db22
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: Kuru Exchange: Market-MON/USDC
21 conflicts on slot 0x79b05f7b6c…2d32da
Audit this contract →
← previous block·next block →recent activity