← previous blocknext block →recent activity
Analyzing
Block #100,161,896
13 transactions · 12 stateful · 2026-08-29 10:35:34 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,161,896 · 13 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52e0faa1…d718
0x34b655…2a6f
4 touches
1 conflict
0x10379e8d…3675
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xae279cbe…e7a0
0x21e325…7777
2 touches
0 conflicts
0xbc467e7a…af36
0x21e325…7777
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x45885570…ed97
0x34b655…2a6f
2 touches
0 conflicts
0x54b965f1…42c9
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 0x52e0faa1cd…a7d718
Audit this contract →
← previous block·next block →recent activity