← previous blocknext block →recent activity
Analyzing
Block #74,429,326
30 transactions · 21 stateful · 2026-05-14 00:33:49 UTC
Parallelism
87/100
Blocked
48%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,429,326 · 30 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
2w05w16w27w28w09w115w316w017w118w220w222w324w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x765c236f…ff45
0x2a68ba…90c5
6 touches
3 conflicts
0x95d93988…00f8
0x065c9d…c394
5 touches
3 conflicts
0xe4f6be23…c84d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0x094452…0a09
4 touches
1 conflict
0x00000000…0002
0x094452…0a09
4 touches
1 conflict
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
3 conflicts on slot 0xc3c8642ae9…317da5
Audit this contract →
← previous block·next block →recent activity