← previous blocknext block →recent activity
Analyzing
Block #100,064,474
17 transactions · 16 stateful · 2026-08-29 02:24:55 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,064,474 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w210w111w213w314w416w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb52895d6…7dc6
0x34b655…2a6f
8 touches
6 conflicts
0xa11b60f7…8e8b
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5ecbbe42…e861
0x34b655…2a6f
4 touches
1 conflict
0x9ca6fa7b…aeb3
0x34b655…2a6f
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
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
6 conflicts on slot 0xb52895d67b…107dc6
Audit this contract →
← previous block·next block →recent activity