← previous blocknext block →recent activity
Analyzing
Block #73,334,835
12 transactions · 11 stateful · 2026-05-08 22:52:20 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,334,835 · 12 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
1w05w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0x93e8dfe6…e63f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x227162fd…fbeb
0x065c9d…c394
2 touches
0 conflicts
0x3bc02844…0ef3
0x065c9d…c394
2 touches
0 conflicts
0x4a2ac18e…9c46
0x065c9d…c394
2 touches
0 conflicts
0x4d715883…2942
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity