← previous blocknext block →recent activity
Analyzing
Block #97,916,448
14 transactions · 14 stateful · 2026-08-21 13:13:25 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,916,448 · 14 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
1w02w14w06w17w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48355ddc…a4f8
0x34b655…2a6f
4 touches
1 conflict
0x442bebe3…6650
0x34b655…2a6f
4 touches
1 conflict
0x8f5fdd0a…6c4c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0019
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0029
0x1b6862…e19c
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 0x48355ddcb1…75a4f8
Audit this contract →
← previous block·next block →recent activity