← previous blocknext block →recent activity
Analyzing
Block #116,897,914
15 transactions · 11 stateful · 2026-10-27 00:25:00 UTC
Parallelism
73/100
Blocked
55%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #116,897,914 · 15 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
1w02w13w24w310w111w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd808de1…5c3c
0x34b655…2a6f
8 touches
6 conflicts
0xf5dc501b…831c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x522b5ecd…4efe
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0055
0x1b6862…e19c
6 touches
3 conflicts
0x5057d7be…407c
0x1b6862…e19c
6 touches
3 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
6 conflicts on slot 0xfd808de135…295c3c
Audit this contract →
← previous block·next block →recent activity