← previous blocknext block →recent activity
Analyzing
Block #74,978,151
8 transactions · 8 stateful · 2026-05-16 13:42:19 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,978,151 · 8 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
1w02w15w26w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb39a388…8d75
0x065c9d…c394
4 touches
1 conflict
0x0a5350e9…e5c3
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0xfd14e9a0…566b
0x065c9d…c394
3 touches
1 conflict
0x8a904db9…2067
0x065c9d…c394
3 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
2 touches
0 conflicts
0x968bdacb…f461
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 0xdb39a388f3…8e8d75
Audit this contract →
← previous block·next block →recent activity