← previous blocknext block →recent activity
Analyzing
Block #74,384,368
13 transactions · 11 stateful · 2026-05-13 19:34:37 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,384,368 · 13 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
3w04w05w17w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x22f3622e…7189
0x065c9d…c394
2 touches
0 conflicts
0x409da52d…c7a5
0x065c9d…c394
2 touches
0 conflicts
0x4dd05d17…42eb
0x065c9d…c394
2 touches
0 conflicts
0x556bf24a…9341
0x065c9d…c394
2 touches
0 conflicts
0x746c16ec…ad87
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