← previous blocknext block →recent activity
Analyzing
Block #98,385,392
10 transactions · 10 stateful · 2026-08-23 04:37:56 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,385,392 · 10 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
5w07w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb282d0ed…3561
0x34b655…2a6f
4 touches
1 conflict
0x0b9bbe33…ca1b
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
0x34b655…2a6f
4 touches
1 conflict
0x3750b746…5a9e
0x34b655…2a6f
2 touches
0 conflicts
0x3c5ea1e9…7e5a
0x34b655…2a6f
2 touches
0 conflicts
0x3dc5798b…5c87
0x34b655…2a6f
2 touches
0 conflicts
0x46f868db…5444
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity