← previous blocknext block →recent activity
Analyzing
Block #100,121,969
17 transactions · 14 stateful · 2026-08-29 07:14:25 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,121,969 · 17 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
1w02w13w04w19w010w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaeb46f64…7cfc
0xaca92e…35da
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0562cb77…a03b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x1c8a33…d316
2 touches
0 conflicts
0x55bacc38…fc8a
0x1c8a33…d316
2 touches
0 conflicts
0x12f129f2…fe6b
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186b
0x2b46c0…1669
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity