← previous blocknext block →recent activity
Analyzing
Block #100,022,420
19 transactions · 16 stateful · 2026-08-28 22:53:15 UTC
Parallelism
89/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,022,420 · 19 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
1w04w07w111w012w115w016w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0x659933ab…e189
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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 0x2c2db8e9ef…f4fdc7
Audit this contract →
← previous block·next block →recent activity