← previous blocknext block →recent activity
Analyzing
Block #100,595,499
21 transactions · 19 stateful · 2026-08-30 23:01:02 UTC
Parallelism
90/100
Blocked
16%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,595,499 · 21 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w08w110w011w012w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76622fb2…4f08
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x5dda0222…bf9c
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd1e8cb72…94cf
0xd32edf…ff58
3 touches
1 conflict
0x8ddeba74…fd50
0x34b655…2a6f
2 touches
0 conflicts
0x8ff85b19…dde0
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 0x76622fb2e3…024f08
Audit this contract →
← previous block·next block →recent activity