← previous blocknext block →recent activity
Analyzing
Block #100,620,782
14 transactions · 14 stateful · 2026-08-31 01:08:14 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,620,782 · 14 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
2w03w17w08w19w210w012w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0xe4f6e7…9657
6 touches
3 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
6 touches
3 conflicts
0x00000000…0008
0x0ea966…0742
6 touches
3 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
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: 0xe4f6e757…919657
3 conflicts on slot 0x44ad89ba62…49cf83
Audit this contract →
← previous block·next block →recent activity