← previous blocknext block →recent activity
Analyzing
Block #98,748,513
27 transactions · 13 stateful · 2026-08-24 11:41:03 UTC
Parallelism
89/100
Blocked
31%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,748,513 · 27 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
2w04w15w29w025w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x5a99808d…88e1
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf2410d5d…8153
0x34b655…2a6f
4 touches
1 conflict
0x08943ea2…ed03
0x754704…b603
2 touches
0 conflicts
0x00000000…0000
0x094452…0a09
2 touches
0 conflicts
0x00000000…0002
0x094452…0a09
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
3 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity