← previous blocknext block →recent activity
Analyzing
Block #100,986,190
18 transactions · 16 stateful · 2026-09-01 07:46:44 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,986,190 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w08w19w210w311w312w414w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ee8b564…4c49
0x34b655…2a6f
12 touches
15 conflicts
0xa9988419…9f45
0x34b655…2a6f
8 touches
6 conflicts
0x5ecbec8a…cdab
0x34b655…2a6f
8 touches
6 conflicts
0x52749b2c…53c4
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x42522e76…2592
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: Perpl
15 conflicts on slot 0x3ee8b5644d…f04c49
Audit this contract →
← previous block·next block →recent activity