← previous blocknext block →recent activity
Analyzing
Block #72,928,996
11 transactions · 9 stateful · 2026-05-07 01:52:05 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,928,996 · 11 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
3w04w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e66da19…66b6
0x065c9d…c394
4 touches
1 conflict
0x41335ddf…94b9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x186e7f62…90a8
0x065c9d…c394
2 touches
0 conflicts
0x2a354a63…0515
0x065c9d…c394
2 touches
0 conflicts
0x2be309d8…395e
0x065c9d…c394
2 touches
0 conflicts
0x2f185edc…a713
0x065c9d…c394
2 touches
0 conflicts
0x453b178e…acf9
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 0x8e66da1932…c966b6
Audit this contract →
← previous block·next block →recent activity