← previous blocknext block →recent activity
Analyzing
Block #74,310,222
12 transactions · 9 stateful · 2026-05-13 11:21:22 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,310,222 · 12 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
1w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde59d190…0ec1
0x065c9d…c394
4 touches
1 conflict
0x6fe133de…05bb
0x065c9d…c394
4 touches
1 conflict
0xb86b1171…d684
0x065c9d…c394
3 touches
1 conflict
0xc8d98fee…e82c
0x065c9d…c394
3 touches
1 conflict
0x6c9fe49d…8f60
0x065c9d…c394
2 touches
0 conflicts
0x79314b38…5801
0x065c9d…c394
2 touches
0 conflicts
0xb50d0776…79fb
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
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 0xde59d190f1…bc0ec1
Audit this contract →
← previous block·next block →recent activity