← previous blocknext block →recent activity
Analyzing
Block #98,100,721
44 transactions · 36 stateful · 2026-08-22 04:45:01 UTC
Parallelism
70/100
Blocked
64%
Avg conflicts / tx
1.57
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #98,100,721 · 44 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w18w09w110w211w315w016w117w224w325w426w527w628w729w830w932w1035w438w239w343w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x6cd6078c…7e9b
0x34b655…2a6f
8 touches
6 conflicts
0x556a9a7a…b0ae
0x34b655…2a6f
6 touches
3 conflicts
0x6df1d50f…8a92
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity