← previous blocknext block →recent activity
Analyzing
Block #98,991,452
19 transactions · 16 stateful · 2026-08-25 08:03:38 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,991,452 · 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
8w013w115w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x354e383e…817c
0xa6afd3…d132
4 touches
1 conflict
0xf0381cf8…7b47
0xa6afd3…d132
3 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0xe849d2c3…8050
0x40c49f…2af0
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
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: Perpl
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity