← previous blocknext block →recent activity
Analyzing
Block #98,755,432
19 transactions · 19 stateful · 2026-08-24 12:15:58 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,755,432 · 19 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
2w03w15w06w18w09w210w111w012w015w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x10a81eed…c249
0x340143…768f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xc871c5f0…84af
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0000
0x5d98f1…8bb2
4 touches
1 conflict
0x5216debe…5327
0x5d98f1…8bb2
4 touches
1 conflict
0x0b552eae…fbd9
0x754704…b603
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity