← previous blocknext block →recent activity
Analyzing
Block #73,377,386
16 transactions · 13 stateful · 2026-05-09 03:35:23 UTC
Parallelism
63/100
Blocked
46%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,377,386 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w19w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x22e295f5…1bef
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x7fb38b87…dd60
0x065c9d…c394
4 touches
1 conflict
0xc213b3ac…2bc0
0x065c9d…c394
3 touches
1 conflict
0x876ed576…89d1
0x065c9d…c394
3 touches
1 conflict
0xa5e1d712…943d
0x065c9d…c394
3 touches
1 conflict
0x6ac82a9d…12a3
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: MarginAccount
10 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity