← previous blocknext block →recent activity
Analyzing
Block #74,248,316
7 transactions · 6 stateful · 2026-05-13 04:29:39 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,248,316 · 7 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
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0xe5c732bf…c37c
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x04c38950…2f02
0x065c9d…c394
2 touches
0 conflicts
0x52ced83a…4bda
0x065c9d…c394
2 touches
0 conflicts
0x832be6ae…3d06
0x065c9d…c394
2 touches
0 conflicts
0x86db1bb0…e7c2
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