← previous blocknext block →recent activity
Analyzing
Block #101,667,039
15 transactions · 15 stateful · 2026-09-03 16:52:33 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,667,039 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w510w011w113w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x450fb5b7…9760
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0005
0x106d0e…1433
2 touches
0 conflicts
0x00000000…0008
0x106d0e…1433
2 touches
0 conflicts
0x00000000…000c
0x106d0e…1433
2 touches
0 conflicts
0x00000000…000d
0x106d0e…1433
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity