← previous blocknext block →recent activity
Analyzing
Block #100,851,413
23 transactions · 20 stateful · 2026-08-31 20:28:48 UTC
Parallelism
83/100
Blocked
55%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,851,413 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w28w09w110w011w112w014w217w118w219w220w321w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
6 touches
3 conflicts
0x51cfbcbc…fa29
0x34b655…2a6f
6 touches
3 conflicts
0x6bf71f68…fd07
0x34b655…2a6f
6 touches
3 conflicts
0xdd683444…08a4
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004f
0x80c745…7210
6 touches
3 conflicts
0x743c0e3f…2f5f
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: MarginAccount
3 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity