← previous blocknext block →recent activity
Analyzing
Block #100,630,403
17 transactions · 13 stateful · 2026-08-31 01:56:38 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,630,403 · 17 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
6w010w011w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6719a767…9d62
0x34b655…2a6f
4 touches
1 conflict
0x6d5c5d72…914b
0x34b655…2a6f
4 touches
1 conflict
0x7db78f05…2895
0x34b655…2a6f
4 touches
1 conflict
0xbcdd58ff…0711
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0x0a78cc73…b34d
0x34b655…2a6f
4 touches
1 conflict
0x4690a385…779b
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0x6719a76784…b59d62
Audit this contract →
← previous block·next block →recent activity