← previous blocknext block →recent activity
Analyzing
Block #73,324,099
19 transactions · 17 stateful · 2026-05-08 21:40:59 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.37
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,324,099 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w28w19w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xf537eaa0…73c8
0x065c9d…c394
6 touches
3 conflicts
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xd1cf570f…2d37
0x065c9d…c394
4 touches
1 conflict
0xd362b834…bca6
0x065c9d…c394
4 touches
1 conflict
0x5ed6b55b…3904
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity