← previous blocknext block →recent activity
Analyzing
Block #74,395,931
7 transactions · 6 stateful · 2026-05-13 20:51:34 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,395,931 · 7 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8041dd1…50d4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x27ba8b32…df07
0x065c9d…c394
4 touches
1 conflict
0x1150fcd4…5441
0x065c9d…c394
2 touches
0 conflicts
0x26c5ada7…0124
0x065c9d…c394
2 touches
0 conflicts
0x3f08a853…eea2
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x61be6cec…628a
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 0xf8041dd18d…c250d4
Audit this contract →
← previous block·next block →recent activity