← previous blocknext block →recent activity
Analyzing
Block #72,973,950
16 transactions · 12 stateful · 2026-05-07 06:51:05 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,973,950 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w08w19w210w311w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x7f189cf6…afab
0x065c9d…c394
4 touches
1 conflict
0x19725b1a…2b93
0x34b655…2a6f
4 touches
1 conflict
0x3b2a4ff1…3af7
0x34b655…2a6f
4 touches
1 conflict
0xf4730a2d…3538
0x34b655…2a6f
4 touches
1 conflict
0x33018431…8f5e
0x188d58…ea8e
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity