← previous blocknext block →recent activity
Analyzing
Block #98,443,004
16 transactions · 14 stateful · 2026-08-23 09:27:48 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,443,004 · 16 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
1w05w17w211w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7aad02c6…b979
0x34b655…2a6f
10 touches
10 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
8 touches
6 conflicts
0x7c82b710…e9a9
0x34b655…2a6f
6 touches
3 conflicts
0xf2e838c8…1b9f
0x34b655…2a6f
4 touches
1 conflict
0x077d58c3…8ed7
0x34b655…2a6f
4 touches
1 conflict
0x23e95a3a…7669
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
15 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity