← previous blocknext block →recent activity
Analyzing
Block #74,788,872
11 transactions · 9 stateful · 2026-05-15 16:38:12 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,788,872 · 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
2w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x276cbbd3…7faa
0x065c9d…c394
4 touches
1 conflict
0x45a454f0…98fb
0x065c9d…c394
3 touches
1 conflict
0x76118d13…c8bc
0x065c9d…c394
3 touches
1 conflict
0x06de1c48…920b
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0xe6f3ee49…2cdb
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…000b
0x5d823e…89c6
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 0x276cbbd3f0…0f7faa
Audit this contract →
← previous block·next block →recent activity