← previous blocknext block →recent activity
Analyzing
Block #92,187,443
12 transactions · 12 stateful · 2026-08-01 11:13:39 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,187,443 · 12 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
2w03w04w16w18w210w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x28eb3d1e…034b
0x34b655…2a6f
4 touches
1 conflict
0x4bc1abab…5874
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x91855e…ac7e
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x93cf7a97…7c6d
0x065c9d…c394
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity