← previous blocknext block →recent activity
Analyzing
Block #98,939,828
18 transactions · 18 stateful · 2026-08-25 03:43:53 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,939,828 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w015w016w117w2
- 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
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0x41335ddf…94b9
0x34b655…2a6f
4 touches
1 conflict
0x260cc5c4…bef0
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…1869
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186a
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186d
0x2b46c0…1669
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