← previous blocknext block →recent activity
Analyzing
Block #74,388,083
23 transactions · 14 stateful · 2026-05-13 19:59:18 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,388,083 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x248748c4…84a2
0x065c9d…c394
2 touches
0 conflicts
0x2b5faf6c…ba13
0x065c9d…c394
2 touches
0 conflicts
0x75a54c01…4915
0x065c9d…c394
2 touches
0 conflicts
0x871db4b3…4a3e
0x065c9d…c394
2 touches
0 conflicts
0x9ba84f5c…a63b
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity