← previous blocknext block →recent activity
Analyzing
Block #74,453,592
18 transactions · 13 stateful · 2026-05-14 03:15:22 UTC
Parallelism
89/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,453,592 · 18 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
3w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbc942767…8edf
0x065c9d…c394
3 touches
1 conflict
0x0f069dca…8c8b
0x065c9d…c394
3 touches
1 conflict
0x936fdcd7…a0c1
0x065c9d…c394
2 touches
0 conflicts
0x6f2b871a…04ea
0x18c6fe…7777
2 touches
0 conflicts
0x9995a2da…c008
0x18c6fe…7777
2 touches
0 conflicts
0x194f2c02…19e6
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity