← previous blocknext block →recent activity
Analyzing
Block #100,561,654
26 transactions · 23 stateful · 2026-08-30 20:10:47 UTC
Parallelism
92/100
Blocked
30%
Avg conflicts / tx
0.35
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,561,654 · 26 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
5w06w07w08w19w010w111w114w017w119w120w021w124w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0de3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x261cbea7…e35d
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 0xe1c4e5ce15…770de3
Audit this contract →
← previous block·next block →recent activity