← previous blocknext block →recent activity
Analyzing
Block #99,079,898
114 transactions · 109 stateful · 2026-08-25 15:35:02 UTC
Parallelism
96/100
Blocked
6%
Avg conflicts / tx
0.05
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,079,898 · 114 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
1w02w17w111w012w1110w2112w2113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d5d1fb5…86a7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21bf
0x1b6862…e19c
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
1 conflict on slot 0x6d5d1fb525…a986a7
Audit this contract →
← previous block·next block →recent activity