← previous blocknext block →recent activity
Analyzing
Block #98,424,650
19 transactions · 18 stateful · 2026-08-23 07:55:28 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,424,650 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w28w311w312w413w416w117w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66e5ca4f…1d09
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x803bf237…2cc1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49028f08…fcc8
0x34b655…2a6f
4 touches
1 conflict
0x7385d4c3…4e05
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 0x66e5ca4fd0…9d1d09
Audit this contract →
← previous block·next block →recent activity