← previous blocknext block →recent activity
Analyzing
Block #99,473,913
10 transactions · 10 stateful · 2026-08-27 00:38:21 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,473,913 · 10 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
2w05w16w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22ee94ac…aee8
0x065c9d…c394
2 touches
0 conflicts
0x95ca748b…ae16
0x065c9d…c394
2 touches
0 conflicts
0x9eb504c5…6d65
0x065c9d…c394
2 touches
0 conflicts
0xb5a44030…5c28
0x065c9d…c394
2 touches
0 conflicts
0xdbc82007…4e8c
0x065c9d…c394
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity