← previous blocknext block →recent activity
Analyzing
Block #98,473,715
16 transactions · 16 stateful · 2026-08-23 12:02:40 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,473,715 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w011w112w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbff3a360…6ae5
0x34b655…2a6f
4 touches
1 conflict
0xc7f6eab9…9e9f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe26c4e53…94c2
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb42e8645…3962
0x34b655…2a6f
4 touches
1 conflict
0xeaced15b…2221
0x754704…b603
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 0xbff3a360e1…d56ae5
Audit this contract →
← previous block·next block →recent activity