← previous blocknext block →recent activity
Analyzing
Block #73,478,916
17 transactions · 11 stateful · 2026-05-09 14:51:02 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,478,916 · 17 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
1w05w09w110w015w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae69c125…2379
0x2a68ba…90c5
4 touches
1 conflict
0x0f9b918b…212d
0x34b655…2a6f
4 touches
1 conflict
0x6061827a…be38
0x065c9d…c394
3 touches
1 conflict
0x3afb63a8…bb81
0xd32edf…ff58
3 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x264c6e4e…cbb6
0x3bd359…433a
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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 0xae69c12575…722379
Audit this contract →
← previous block·next block →recent activity