← previous blocknext block →recent activity
Analyzing
Block #99,211,944
6 transactions · 6 stateful · 2026-08-26 02:39:40 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,211,944 · 6 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe4dac54…0663
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0d03bddb…6658
0x34b655…2a6f
2 touches
0 conflicts
0x295780b7…d2d1
0x34b655…2a6f
2 touches
0 conflicts
0x35c3d4d5…9375
0x34b655…2a6f
2 touches
0 conflicts
0x605218e1…ebbc
0x34b655…2a6f
2 touches
0 conflicts
0x9b2d3bee…8eeb
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0xbe4dac54ab…f60663
Audit this contract →
← previous block·next block →recent activity