← previous blocknext block →recent activity
Analyzing
Block #74,563,272
10 transactions · 9 stateful · 2026-05-14 15:30:56 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,563,272 · 10 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
1w04w05w17w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ba08a85…3466
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0x4f8ea2…84fb
4 touches
1 conflict
0xf7b8c299…d1d8
0x065c9d…c394
4 touches
1 conflict
0xd4bf6c2b…980a
0x065c9d…c394
3 touches
1 conflict
0x79bf7f3e…44b1
0x065c9d…c394
3 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x765c236f…ff45
0x2a68ba…90c5
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 0x1ba08a857b…0e3466
Audit this contract →
← previous block·next block →recent activity