← previous blocknext block →recent activity
Analyzing
Block #100,810,748
93 transactions · 90 stateful · 2026-08-31 17:04:02 UTC
Parallelism
96/100
Blocked
8%
Avg conflicts / tx
0.1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,810,748 · 93 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
2w03w14w012w013w114w115w286w291w292w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14fb4c2a…2d8d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x18a01188…42f0
0x851145…3f07
4 touches
1 conflict
0x992d3412…2cc3
0x851145…3f07
4 touches
1 conflict
0xa538600d…3da5
0x851145…3f07
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
3 conflicts on slot 0x14fb4c2aec…962d8d
Audit this contract →
← previous block·next block →recent activity