← previous blocknext block →recent activity
Analyzing
Block #74,356,784
8 transactions · 7 stateful · 2026-05-13 16:31:01 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,356,784 · 8 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4923aad5…5815
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6eee9f9e…2c25
0x065c9d…c394
4 touches
1 conflict
0xbbdf99c9…2f1e
0x065c9d…c394
3 touches
1 conflict
0x66d18879…a6d4
0x065c9d…c394
2 touches
0 conflicts
0x8427451e…7622
0x065c9d…c394
2 touches
0 conflicts
0x194f2c02…19e6
0x2a68ba…90c5
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 0x4923aad560…a95815
Audit this contract →
← previous block·next block →recent activity