← previous blocknext block →recent activity
Analyzing
Block #73,324,101
19 transactions · 15 stateful · 2026-05-08 21:41:00 UTC
Parallelism
89/100
Blocked
20%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,324,101 · 19 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
1w04w111w012w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x7f8ee36d…3864
0x065c9d…c394
2 touches
0 conflicts
0xb08cbaf1…aa9c
0x065c9d…c394
2 touches
0 conflicts
0xd8d56335…f2e7
0x065c9d…c394
2 touches
0 conflicts
0xf22f7e88…7fc2
0x065c9d…c394
2 touches
0 conflicts
0xf8bf6740…1219
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: MarginAccount
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity