← previous blocknext block →recent activity
Analyzing
Block #98,569,348
15 transactions · 15 stateful · 2026-08-23 20:17:05 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,569,348 · 15 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
4w05w17w09w010w111w012w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3981be5…2c47
0x34b655…2a6f
6 touches
3 conflicts
0xec1f8387…c83d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x9c3004b2…5421
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xb4bebc9f…a381
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
3 conflicts on slot 0xf3981be56e…f02c47
Audit this contract →
← previous block·next block →recent activity