← previous blocknext block →recent activity
Analyzing
Block #98,063,622
25 transactions · 21 stateful · 2026-08-22 01:38:20 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,063,622 · 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
1w02w04w17w28w310w011w113w014w116w017w220w324w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xbb3f3c…e046
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x2130a548…c1de
0x34b655…2a6f
4 touches
1 conflict
0x297de2d5…7396
0x34b655…2a6f
4 touches
1 conflict
0x41c52e32…c46a
0x34b655…2a6f
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity