← previous blocknext block →recent activity
Analyzing
Block #94,953,278
10 transactions · 10 stateful · 2026-08-11 03:23:59 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,953,278 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9c3e42f3…2b3b
0x851145…3f07
4 touches
1 conflict
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity