← previous blocknext block →recent activity
Analyzing
Block #98,472,796
35 transactions · 24 stateful · 2026-08-23 11:58:03 UTC
Parallelism
89/100
Blocked
42%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,472,796 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w211w312w114w015w117w018w022w123w125w129w231w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xf032cc0b…b8ea
0xa6afd3…d132
5 touches
3 conflicts
0xbad0ac8d…f430
0xd32edf…ff58
5 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
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
3 conflicts on slot 0xd6bd849ae7…7c5597
Audit this contract →
← previous block·next block →recent activity