← previous blocknext block →recent activity
Analyzing
Block #100,728,976
14 transactions · 14 stateful · 2026-08-31 10:12:29 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,728,976 · 14 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
2w05w19w010w211w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1894e7f…30fe
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x528eaa34…e497
0x34b655…2a6f
4 touches
1 conflict
0x5a95f394…be66
0x34b655…2a6f
4 touches
1 conflict
0x69844665…da8c
0x34b655…2a6f
4 touches
1 conflict
0x7d0343fe…08b5
0x34b655…2a6f
4 touches
1 conflict
0x8ba18cc2…5afd
0x34b655…2a6f
4 touches
1 conflict
0x932a9590…0b19
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
1 conflict on slot 0xf1894e7f22…6c30fe
Audit this contract →
← previous block·next block →recent activity