← previous blocknext block →recent activity
Analyzing
Block #98,750,012
12 transactions · 12 stateful · 2026-08-24 11:48:35 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,750,012 · 12 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
1w04w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x61f2e4cd…4dd9
0x065c9d…c394
2 touches
0 conflicts
0x659ddcbd…9283
0x065c9d…c394
2 touches
0 conflicts
0x6d4aab55…74ae
0x065c9d…c394
2 touches
0 conflicts
0x991ade75…938e
0x065c9d…c394
2 touches
0 conflicts
0xacf47e9b…1fa8
0x065c9d…c394
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