← previous blocknext block →recent activity
Analyzing
Block #98,333,063
18 transactions · 14 stateful · 2026-08-23 00:14:41 UTC
Parallelism
89/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,333,063 · 18 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
3w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x9a8f8e94…d921
0x065c9d…c394
4 touches
1 conflict
0x00000000…0007
0x340143…768f
2 touches
0 conflicts
0xf5dc501b…8313
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0031
0x59df86…2780
2 touches
0 conflicts
0x81955a0a…29ee
0x6657d1…8ccc
2 touches
0 conflicts
0xd9a3b4fb…c549
0x6657d1…8ccc
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