← previous blocknext block →recent activity
Analyzing
Block #98,090,781
27 transactions · 22 stateful · 2026-08-22 03:55:00 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,090,781 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w010w011w113w215w216w317w118w020w021w122w324w425w526w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bd1c200…56de
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x3e04662b…0da5
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x3836a730…b3a9
0x34b655…2a6f
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 0x2bd1c2000c…7d56de
Audit this contract →
← previous block·next block →recent activity