← previous blocknext block →recent activity
Analyzing
Block #101,972,506
17 transactions · 16 stateful · 2026-09-04 18:32:24 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,972,506 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w19w011w013w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb1b66a1…ce4e
0x34b655…2a6f
4 touches
1 conflict
0xb47d4bdd…6172
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd35de5e7…e1cd
0x34b655…2a6f
4 touches
1 conflict
0xe8f860c0…35c9
0x34b655…2a6f
4 touches
1 conflict
0x04d4f30d…4dfb
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
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
1 conflict on slot 0xeb1b66a1ed…55ce4e
Audit this contract →
← previous block·next block →recent activity