← previous blocknext block →recent activity
Analyzing
Block #74,510,005
11 transactions · 11 stateful · 2026-05-14 09:31:30 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,510,005 · 11 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
1w05w16w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd5a7018a…f881
0x065c9d…c394
3 touches
1 conflict
0x08b54a43…0607
0x065c9d…c394
3 touches
1 conflict
0x7b8a46eb…a3c4
0x065c9d…c394
2 touches
0 conflicts
0x7b96c508…5700
0x065c9d…c394
2 touches
0 conflicts
0xa7fdb62b…4310
0x065c9d…c394
2 touches
0 conflicts
0xdb9d90c4…7ded
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity