← previous blocknext block →recent activity
Analyzing
Block #74,787,599
13 transactions · 10 stateful · 2026-05-15 16:29:41 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,787,599 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e27b832…f5c3
0x065c9d…c394
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x765c236f…ff45
0x2a68ba…90c5
8 touches
6 conflicts
0x2883bf78…5f1c
0xd32edf…ff58
5 touches
3 conflicts
0x65bd5770…5ecc
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x09000000…0007
0x000000…1000
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
6 conflicts on slot 0x7e27b832f5…21f5c3
Audit this contract →
← previous block·next block →recent activity