← previous blocknext block →recent activity
Analyzing
Block #98,100,473
19 transactions · 19 stateful · 2026-08-22 04:43:47 UTC
Parallelism
84/100
Blocked
32%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,100,473 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w16w07w113w114w217w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cd6078c…7e9b
0x34b655…2a6f
6 touches
3 conflicts
0xb64473b0…0d6f
0xc8689a…ee79
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0x5b01c59e…cfd0
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xa67acdc8…1d9c
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 0x6cd6078c74…697e9b
Audit this contract →
← previous block·next block →recent activity