← previous blocknext block →recent activity
Analyzing
Block #98,100,940
19 transactions · 17 stateful · 2026-08-22 04:46:08 UTC
Parallelism
89/100
Blocked
18%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,100,940 · 19 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
1w03w04w08w19w010w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0xc0a73ae2…2e95
0x34b655…2a6f
4 touches
1 conflict
0x53bda555…3810
0x34b655…2a6f
4 touches
1 conflict
0x4d016985…d5ef
0x34b655…2a6f
4 touches
1 conflict
0x3c78ca04…432c
0x34b655…2a6f
4 touches
1 conflict
0x87dacc7a…3223
0x065c9d…c394
4 touches
1 conflict
0x396c7608…b464
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
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 0xd6bd849ae7…7c5597
Audit this contract →
← previous block·next block →recent activity