← previous blocknext block →recent activity
Analyzing
Block #101,301,741
19 transactions · 16 stateful · 2026-09-02 10:14:37 UTC
Parallelism
84/100
Blocked
19%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,301,741 · 19 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
2w03w113w014w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6266e26a…96ef
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x2e8d86f6…d55c
0x065c9d…c394
4 touches
1 conflict
0x6266e26a…96ee
0x34b655…2a6f
4 touches
1 conflict
0x48ed1159…abe9
0x34ae4d…3fc5
2 touches
0 conflicts
0x024b482b…16b0
0x34b655…2a6f
2 touches
0 conflicts
0x0f14cd85…cfcc
0x34b655…2a6f
2 touches
0 conflicts
0x1b7933ad…27a1
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 0x6266e26a7e…5096ef
Audit this contract →
← previous block·next block →recent activity