← previous blocknext block →recent activity
Analyzing
Block #98,026,545
25 transactions · 22 stateful · 2026-08-21 22:31:46 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,026,545 · 25 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
1w02w13w06w28w09w114w022w123w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3836a730…b3a9
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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…001b
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 0x3836a73066…21b3a9
Audit this contract →
← previous block·next block →recent activity