← previous blocknext block →recent activity
Analyzing
Block #100,635,009
12 transactions · 12 stateful · 2026-08-31 02:19:48 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,635,009 · 12 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
1w02w17w08w19w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x641aed07…bcb9
0x34b655…2a6f
4 touches
1 conflict
0x6caf33e2…c261
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf574b26e…a6e7
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x315e07b8…9823
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
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 0x641aed075a…00bcb9
Audit this contract →
← previous block·next block →recent activity