← previous blocknext block →recent activity
Analyzing
Block #72,973,779
8 transactions · 6 stateful · 2026-05-07 06:49:57 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,973,779 · 8 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b8b5daf…d2f1
0x065c9d…c394
4 touches
1 conflict
0x4da57732…c2d8
0x065c9d…c394
3 touches
1 conflict
0x5b118836…778a
0x065c9d…c394
3 touches
1 conflict
0x2b02f616…02f2
0x065c9d…c394
2 touches
0 conflicts
0x7d4357d4…ed25
0x065c9d…c394
2 touches
0 conflicts
0x7f189cf6…afab
0x065c9d…c394
2 touches
0 conflicts
0x7f3b1f9c…b9e9
0x065c9d…c394
2 touches
0 conflicts
0xac792ec8…e46f
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 0x0b8b5daf85…3dd2f1
Audit this contract →
← previous block·next block →recent activity