← previous blocknext block →recent activity
Analyzing
Block #74,360,154
23 transactions · 10 stateful · 2026-05-13 16:53:23 UTC
Parallelism
91/100
Blocked
20%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,360,154 · 23 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
1w016w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a8e4931…bb03
0x065c9d…c394
4 touches
1 conflict
0x40ecd90c…10ed
0x065c9d…c394
4 touches
1 conflict
0xd4c42d34…5992
0x065c9d…c394
3 touches
1 conflict
0x7e8c7a19…1480
0x065c9d…c394
3 touches
1 conflict
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x62eb8f2e…f20a
0x065c9d…c394
2 touches
0 conflicts
0x64c35644…937a
0x065c9d…c394
2 touches
0 conflicts
0x6eee9f9e…2c25
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 0x7a8e493133…12bb03
Audit this contract →
← previous block·next block →recent activity