← previous blocknext block →recent activity
Analyzing
Block #103,214,188
13 transactions · 12 stateful · 2026-09-09 03:09:35 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,214,188 · 13 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
1w05w06w17w18w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9722304…6ed0
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0505bae8…b4fb
0x34b655…2a6f
4 touches
1 conflict
0x649ed85f…5eb5
0x34b655…2a6f
4 touches
1 conflict
0xc12e55e5…1c07
0x34b655…2a6f
4 touches
1 conflict
0xc6abdbd8…415a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002b
0x1b6862…e19c
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: Perpl
10 conflicts on slot 0xd97223041d…366ed0
Audit this contract →
← previous block·next block →recent activity