← previous blocknext block →recent activity
Analyzing
Block #73,387,808
8 transactions · 8 stateful · 2026-05-09 04:44:44 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,387,808 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe038916c…b1be
0x2a68ba…90c5
4 touches
1 conflict
0xa3faf51a…3e5b
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x4d87512b…897c
0x065c9d…c394
2 touches
0 conflicts
0x51b3154f…17c9
0x065c9d…c394
2 touches
0 conflicts
0x8ca863a5…da1f
0x065c9d…c394
2 touches
0 conflicts
0x9473a13d…2ee8
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 0xe038916c87…fab1be
Audit this contract →
← previous block·next block →recent activity