← previous blocknext block →recent activity
Analyzing
Block #98,914,791
19 transactions · 15 stateful · 2026-08-25 01:37:56 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,914,791 · 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
1w03w14w210w312w216w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x5b09bf44…5907
0xa6afd3…d132
4 touches
1 conflict
0xefc629e7…776d
0xa6afd3…d132
4 touches
1 conflict
0x2a354a63…0515
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x8e66da19…66b6
0x065c9d…c394
4 touches
1 conflict
0x46cb45de…a567
0x188d58…ea8e
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity