← previous blocknext block →recent activity
Analyzing
Block #98,644,424
14 transactions · 10 stateful · 2026-08-24 02:47:53 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,644,424 · 14 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
1w02w14w09w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5784baac…ac7e
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x3b1eee82…f778
0x34b655…2a6f
4 touches
1 conflict
0x6b728ff3…4385
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x09d37b48…12a2
0x34b655…2a6f
3 touches
1 conflict
0x46808ffa…0bac
0x34b655…2a6f
3 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 0x5784baac17…d4ac7e
Audit this contract →
← previous block·next block →recent activity