← previous blocknext block →recent activity
Analyzing
Block #98,388,893
27 transactions · 22 stateful · 2026-08-23 04:55:33 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,388,893 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w19w010w113w014w116w017w219w323w024w126w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92bb4e9d…0f03
0x34b655…2a6f
6 touches
3 conflicts
0x97d26666…1b52
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
3 conflicts on slot 0x92bb4e9d40…fa0f03
Audit this contract →
← previous block·next block →recent activity