← previous blocknext block →recent activity
Analyzing
Block #101,797,894
14 transactions · 14 stateful · 2026-09-04 03:50:44 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,797,894 · 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
2w03w15w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd751d4fc…0b5b
0x34b655…2a6f
6 touches
3 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xd28e195f…37a1
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xd751d4fc37…4b0b5b
Audit this contract →
← previous block·next block →recent activity