← previous blocknext block →recent activity
Analyzing
Block #101,019,664
18 transactions · 16 stateful · 2026-09-01 10:35:12 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,019,664 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w011w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97e4c862…4419
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x1867b653…e61b
0x34b655…2a6f
2 touches
0 conflicts
0x2c2761c0…476e
0x34b655…2a6f
2 touches
0 conflicts
0x3d6c26e5…1b45
0x34b655…2a6f
2 touches
0 conflicts
0x3ebcba29…6dca
0x34b655…2a6f
2 touches
0 conflicts
0x40f0cbff…df7c
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 0x97e4c86258…af4419
Audit this contract →
← previous block·next block →recent activity