← previous blocknext block →recent activity
Analyzing
Block #72,395,281
16 transactions · 14 stateful · 2026-05-04 14:35:45 UTC
Parallelism
75/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,395,281 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xea4fbdc7…bd59
0x065c9d…c394
4 touches
1 conflict
0xe05d19fa…87d1
0x065c9d…c394
4 touches
1 conflict
0xbab1ac80…6a1e
0xd32edf…ff58
3 touches
1 conflict
0x32b81b61…fbbc
0x065c9d…c394
3 touches
1 conflict
0x6d3c0ed0…be15
0x065c9d…c394
3 touches
1 conflict
0x75021934…02cf
0x065c9d…c394
3 touches
1 conflict
0xa312ced7…06e7
0x065c9d…c394
3 touches
1 conflict
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity