← previous blocknext block →recent activity
Analyzing
Block #101,023,353
16 transactions · 13 stateful · 2026-09-01 10:53:46 UTC
Parallelism
81/100
Blocked
15%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,023,353 · 16 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
6w010w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f39ae73…eb13
0x34b655…2a6f
6 touches
3 conflicts
0xdfce7dfe…5053
0x34b655…2a6f
4 touches
1 conflict
0x62552a2a…7897
0x34b655…2a6f
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0xe75ce681…ba61
0x188d58…ea8e
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x178fe051…465a
0x34b655…2a6f
2 touches
0 conflicts
0x49b0842d…0a93
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
3 conflicts on slot 0x6f39ae73b5…9deb13
Audit this contract →
← previous block·next block →recent activity