← previous blocknext block →recent activity
Analyzing
Block #74,284,742
11 transactions · 10 stateful · 2026-05-13 08:31:48 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,284,742 · 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
1w05w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x25e8f4c4…1e2e
0x065c9d…c394
2 touches
0 conflicts
0x2b0b0af5…a623
0x065c9d…c394
2 touches
0 conflicts
0x2f105e88…300a
0x065c9d…c394
2 touches
0 conflicts
0x3dd8b505…aba0
0x065c9d…c394
2 touches
0 conflicts
0xbf756e6e…35d2
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