← previous blocknext block →recent activity
Analyzing
Block #100,724,951
16 transactions · 15 stateful · 2026-08-31 09:52:14 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,724,951 · 16 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
2w03w15w06w07w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbb2fff3…b122
0x34b655…2a6f
4 touches
1 conflict
0x7c68d10b…8386
0x34b655…2a6f
4 touches
1 conflict
0x7f5b2c1d…0e7f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x3ee8b564…4c49
0x34b655…2a6f
4 touches
1 conflict
0x3c2db66e…31bc
0x34b655…2a6f
2 touches
0 conflicts
0xcd26fba5…21c6
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 0xdbb2fff35a…efb122
Audit this contract →
← previous block·next block →recent activity