← previous blocknext block →recent activity
Analyzing
Block #100,849,168
19 transactions · 12 stateful · 2026-08-31 20:17:30 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,849,168 · 19 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
3w05w19w015w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x820d7282…6c34
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xd0f6f4f2…dffa
0x34b655…2a6f
4 touches
1 conflict
0x53d5e848…85ee
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb4c703ab…f8cf
0x34b655…2a6f
4 touches
1 conflict
0x494b6b0d…6817
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
6 conflicts on slot 0x820d72829e…536c34
Audit this contract →
← previous block·next block →recent activity