← previous blocknext block →recent activity
Analyzing
Block #74,302,186
15 transactions · 10 stateful · 2026-05-13 10:27:58 UTC
Parallelism
87/100
Blocked
20%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,302,186 · 15 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
1w02w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x0628b7d7…2e37
0x065c9d…c394
2 touches
0 conflicts
0x138321b9…feca
0x065c9d…c394
2 touches
0 conflicts
0x25757fa3…63ef
0x065c9d…c394
2 touches
0 conflicts
0x34c72c1c…401e
0x065c9d…c394
2 touches
0 conflicts
0x546bc030…1216
0x065c9d…c394
2 touches
0 conflicts
0x910825a2…251a
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