← previous blocknext block →recent activity
Analyzing
Block #74,733,813
12 transactions · 9 stateful · 2026-05-15 10:30:02 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,733,813 · 12 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
1w02w05w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0xd2317da6…644c
0x065c9d…c394
3 touches
1 conflict
0xdedfaf04…b497
0x065c9d…c394
3 touches
1 conflict
0x96b695b8…fafc
0x065c9d…c394
2 touches
0 conflicts
0x9eef31d4…d611
0x065c9d…c394
2 touches
0 conflicts
0xfb6ec3e2…11e0
0x065c9d…c394
2 touches
0 conflicts
0xfcfed5ae…c9ce
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity