← previous blocknext block →recent activity
Analyzing
Block #73,477,095
12 transactions · 10 stateful · 2026-05-09 14:38:54 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,477,095 · 12 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
6w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x6e92cd63…9a82
0x065c9d…c394
4 touches
1 conflict
0x0cfaf810…73a5
0x188d58…ea8e
2 touches
0 conflicts
0x394a7583…ee24
0x188d58…ea8e
2 touches
0 conflicts
0x3ccf0ba5…e16f
0x188d58…ea8e
2 touches
0 conflicts
0x3ccf0ba5…e170
0x188d58…ea8e
2 touches
0 conflicts
0x7c3fa869…7786
0x188d58…ea8e
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 0xc9e9752290…9c3519
Audit this contract →
← previous block·next block →recent activity