← previous blocknext block →recent activity
Analyzing
Block #98,443,418
14 transactions · 14 stateful · 2026-08-23 09:29:53 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,443,418 · 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
1w03w04w05w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb28d6c98…ea8e
0x34b655…2a6f
4 touches
1 conflict
0xc9c17729…ac91
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0c7441d3…34fc
0x34b655…2a6f
2 touches
0 conflicts
0x12d037b7…2111
0x34b655…2a6f
2 touches
0 conflicts
0x3c78ca04…432c
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 0xb28d6c9857…95ea8e
Audit this contract →
← previous block·next block →recent activity