← previous blocknext block →recent activity
Analyzing
Block #98,441,210
24 transactions · 16 stateful · 2026-08-23 09:18:46 UTC
Parallelism
92/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,441,210 · 24 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
5w013w014w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2b181bb8…c7cb
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e70
0x188d58…ea8e
2 touches
0 conflicts
0x21417228…cf0a
0x188d58…ea8e
2 touches
0 conflicts
0x21417228…cf0b
0x188d58…ea8e
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 0xa3ed5a0966…25c6d3
Audit this contract →
← previous block·next block →recent activity