← previous blocknext block →recent activity
Analyzing
Block #74,300,855
8 transactions · 6 stateful · 2026-05-13 10:19:04 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,300,855 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a24eb94…b380
0x065c9d…c394
4 touches
1 conflict
0x0ec7c10b…f7a3
0x065c9d…c394
3 touches
1 conflict
0x6b8c45b6…67cf
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x3ceabd3a…b1b7
0x065c9d…c394
2 touches
0 conflicts
0x3f1fa6d9…11d2
0x065c9d…c394
2 touches
0 conflicts
0x448681c4…7335
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 0x6a24eb9473…30b380
Audit this contract →
← previous block·next block →recent activity