← previous blocknext block →recent activity
Analyzing
Block #98,100,827
25 transactions · 23 stateful · 2026-08-22 04:45:33 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,100,827 · 25 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
1w02w13w04w05w18w110w013w114w215w117w218w219w220w324w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0a73ae2…2e95
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xadbda1a7…5f21
0xa6afd3…d132
6 touches
3 conflicts
0xf88ccd07…a684
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
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
3 conflicts on slot 0xc0a73ae2a1…182e95
Audit this contract →
← previous block·next block →recent activity