← previous blocknext block →recent activity
Analyzing
Block #100,918,836
25 transactions · 19 stateful · 2026-09-01 02:07:56 UTC
Parallelism
88/100
Blocked
42%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,918,836 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w27w010w012w013w115w016w118w120w121w224w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeaef7ff1…c7a2
0x065c9d…c394
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
5 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf2410d5d…8153
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x26489242…c321
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0xeaef7ff10b…58c7a2
Audit this contract →
← previous block·next block →recent activity