← previous blocknext block →recent activity
Analyzing
Block #74,896,495
11 transactions · 10 stateful · 2026-05-16 04:35:58 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,896,495 · 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
2w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e801010…72e6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x06592b22…143b
0x065c9d…c394
3 touches
1 conflict
0xc80c5f35…b7f4
0x065c9d…c394
3 touches
1 conflict
0xe18d254e…5e12
0x065c9d…c394
2 touches
0 conflicts
0xee6daec8…9d2a
0x065c9d…c394
2 touches
0 conflicts
0xef098e13…51f7
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
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 0x1e8010105d…5372e6
Audit this contract →
← previous block·next block →recent activity