← previous blocknext block →recent activity
Analyzing
Block #74,501,384
10 transactions · 8 stateful · 2026-05-14 08:33:28 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,501,384 · 10 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
1w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe409b830…4ba3
0x065c9d…c394
4 touches
1 conflict
0x8386405e…7da7
0x065c9d…c394
3 touches
1 conflict
0x8da885bc…4331
0x065c9d…c394
3 touches
1 conflict
0x58cb839c…60b4
0x065c9d…c394
3 touches
1 conflict
0x833bd424…7a17
0x065c9d…c394
3 touches
1 conflict
0x32881b99…5494
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x81b8e7d1…3ec2
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 0xe409b83015…c64ba3
Audit this contract →
← previous block·next block →recent activity