← previous blocknext block →recent activity
Analyzing
Block #98,071,829
22 transactions · 16 stateful · 2026-08-22 02:19:38 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,071,829 · 22 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
1w02w03w110w012w113w219w020w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d6ebbcf…63e8
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x9dd0a735…4d04
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x7aa91b8f…d070
0x2b46c0…1669
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 0x0d6ebbcf97…7463e8
Audit this contract →
← previous block·next block →recent activity