← previous blocknext block →recent activity
Analyzing
Block #98,984,889
12 transactions · 11 stateful · 2026-08-25 07:30:37 UTC
Parallelism
58/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,984,889 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w09w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x733c7779…a647
0x34b655…2a6f
4 touches
1 conflict
0xbad68552…e6bf
0x34b655…2a6f
4 touches
1 conflict
0xbb1747e2…f78b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x67ef6031…c0da
0x34b655…2a6f
4 touches
1 conflict
0xb5e92bf8…4138
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity