← previous blocknext block →recent activity
Analyzing
Block #100,918,103
21 transactions · 19 stateful · 2026-09-01 02:04:15 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,918,103 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w08w19w011w112w114w215w216w317w418w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc9915b5…542c
0x34b655…2a6f
8 touches
6 conflicts
0x7ff98f24…ca07
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x9dce5f78…29c5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0xdc9915b513…2b542c
Audit this contract →
← previous block·next block →recent activity