← previous blocknext block →recent activity
Analyzing
Block #98,676,064
12 transactions · 10 stateful · 2026-08-24 05:32:47 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,676,064 · 12 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x16e1b61e…017c
0x065c9d…c394
2 touches
0 conflicts
0x104887dc…9894
0x34b655…2a6f
2 touches
0 conflicts
0x10b629c1…3ca7
0x34b655…2a6f
2 touches
0 conflicts
0x32454f9f…67d2
0x34b655…2a6f
2 touches
0 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
2 touches
0 conflicts
0xb6aedce9…a483
0x34b655…2a6f
2 touches
0 conflicts
0xbde524f4…43bf
0x34b655…2a6f
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