← previous blocknext block →recent activity
Analyzing
Block #99,171,371
14 transactions · 14 stateful · 2026-08-25 23:15:32 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,171,371 · 14 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
1w02w13w04w17w111w012w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbfa96f3…54d7
0x34b655…2a6f
4 touches
1 conflict
0xf5142eee…714d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x2bbc0cfb…c2bd
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 0xdbfa96f386…0054d7
Audit this contract →
← previous block·next block →recent activity