← previous blocknext block →recent activity
Analyzing
Block #73,990,057
22 transactions · 17 stateful · 2026-05-11 23:50:25 UTC
Parallelism
91/100
Blocked
24%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,990,057 · 22 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
1w05w06w17w113w014w116w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x65e795ca…0320
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xb560caf0…2127
0x065c9d…c394
3 touches
1 conflict
0x6dc6c7dc…1e42
0x065c9d…c394
2 touches
0 conflicts
0x6f08361d…bda6
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 0x765c236f2d…b5ff45
Audit this contract →
← previous block·next block →recent activity