← previous blocknext block →recent activity
Analyzing
Block #100,704,868
16 transactions · 16 stateful · 2026-08-31 08:11:11 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,704,868 · 16 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
1w03w15w06w17w08w110w012w213w014w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x451e482b…7e7d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x9f26f2cc…a2af
0x34b655…2a6f
4 touches
1 conflict
0xbd7e5778…8896
0x34b655…2a6f
4 touches
1 conflict
0xe42e0954…fa5d
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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 0x451e482b59…427e7d
Audit this contract →
← previous block·next block →recent activity