← previous blocknext block →recent activity
Analyzing
Block #98,939,648
14 transactions · 13 stateful · 2026-08-25 03:42:58 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,939,648 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x41335ddf…94b9
0x34b655…2a6f
4 touches
1 conflict
0xe87576be…02c0
0x34b655…2a6f
4 touches
1 conflict
0x43b34fb2…7b88
0x34b655…2a6f
2 touches
0 conflicts
0x51af0e92…4020
0x34b655…2a6f
2 touches
0 conflicts
0x62efa201…0a74
0x34b655…2a6f
2 touches
0 conflicts
0x63016070…64d5
0x34b655…2a6f
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 0x9a3068dd84…9918f1
Audit this contract →
← previous block·next block →recent activity