← previous blocknext block →recent activity
Analyzing
Block #74,519,096
16 transactions · 11 stateful · 2026-05-14 10:32:47 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,519,096 · 16 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
1w07w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x266cbef1…a976
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x555c788b…5b91
0x1308d7…ff6c
2 touches
0 conflicts
0x6099af6e…db60
0x1308d7…ff6c
2 touches
0 conflicts
0x0872abbe…9c39
0x2a68ba…90c5
2 touches
0 conflicts
0x76e559a4…77fb
0x2a68ba…90c5
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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 0x266cbef1d3…e6a976
Audit this contract →
← previous block·next block →recent activity