← previous blocknext block →recent activity
Analyzing
Block #92,359,584
19 transactions · 15 stateful · 2026-08-02 01:39:23 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,359,584 · 19 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
1w04w08w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc38a969b…3268
0x065c9d…c394
3 touches
1 conflict
0x00f7e3b7…e016
0x188d58…ea8e
2 touches
0 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
2 touches
0 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0xb924350c…7c11
0x754704…b603
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity