← previous blocknext block →recent activity
Analyzing
Block #100,152,653
13 transactions · 11 stateful · 2026-08-29 09:49:02 UTC
Parallelism
62/100
Blocked
45%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,152,653 · 13 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
1w02w03w17w28w39w411w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b37bb6b…aaff
0x34b655…2a6f
6 touches
3 conflicts
0x7083c381…0ce7
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xad37ecd4…9648
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xe5060fe3…ebe8
0x1b6862…e19c
4 touches
1 conflict
0x076ca8d0…8fa0
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 0x5b37bb6bbf…0aaaff
Audit this contract →
← previous block·next block →recent activity