← previous blocknext block →recent activity
Analyzing
Block #98,097,433
14 transactions · 14 stateful · 2026-08-22 04:28:29 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,097,433 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w08w19w010w112w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53eac009…b61b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x5a95f394…be66
0x34b655…2a6f
2 touches
0 conflicts
0x5edabc41…4098
0x34b655…2a6f
2 touches
0 conflicts
0x72f046e0…ed7d
0x34b655…2a6f
2 touches
0 conflicts
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 0x53eac00933…f3b61b
Audit this contract →
← previous block·next block →recent activity