← previous blocknext block →recent activity
Analyzing
Block #74,231,396
11 transactions · 9 stateful · 2026-05-13 02:37:07 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,231,396 · 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
1w03w17w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8b3de3d2…ef33
0xd32edf…ff58
3 touches
1 conflict
0xcbb84c7d…45a6
0x065c9d…c394
2 touches
0 conflicts
0xcd859f86…6734
0x065c9d…c394
2 touches
0 conflicts
0xe10a76da…c58e
0x065c9d…c394
2 touches
0 conflicts
0xe3d92507…b9b0
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity