← previous blocknext block →recent activity
Analyzing
Block #98,100,481
21 transactions · 21 stateful · 2026-08-22 04:43:49 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,100,481 · 21 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
1w02w04w05w18w09w112w213w314w015w117w420w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cd6078c…7e9b
0x34b655…2a6f
10 touches
10 conflicts
0x49914800…d693
0x34b655…2a6f
8 touches
6 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
4 touches
1 conflict
0x10d80fee…dbda
0x2b46c0…1669
4 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x00000000…0007
0x340143…768f
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
10 conflicts on slot 0x6cd6078c74…697e9b
Audit this contract →
← previous block·next block →recent activity