← previous blocknext block →recent activity
Analyzing
Block #100,047,364
23 transactions · 22 stateful · 2026-08-29 00:58:48 UTC
Parallelism
83/100
Blocked
14%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,047,364 · 23 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
2w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d5c5d72…914b
0x34b655…2a6f
8 touches
6 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0x25f658fb…6eba
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
2 touches
0 conflicts
0x4f46a4fb…3224
0x34b655…2a6f
2 touches
0 conflicts
0x4fce3905…6f4f
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
6 conflicts on slot 0x6d5c5d726f…33914b
Audit this contract →
← previous block·next block →recent activity