← previous blocknext block →recent activity
Analyzing
Block #98,071,494
18 transactions · 14 stateful · 2026-08-22 02:17:57 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,071,494 · 18 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
1w02w13w09w010w114w215w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2a6ee72…96b3
0x34b655…2a6f
4 touches
1 conflict
0xb1a75fe3…0fdd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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…001c
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 0xe2a6ee729a…1c96b3
Audit this contract →
← previous block·next block →recent activity