← previous blocknext block →recent activity
Analyzing
Block #101,656,499
14 transactions · 13 stateful · 2026-09-03 15:59:32 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,656,499 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w19w210w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19cb4cde…bfd9
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xf7772b49…fc12
0x34b655…2a6f
4 touches
1 conflict
0xf128b53d…3aa9
0x34b655…2a6f
4 touches
1 conflict
0x0de7749d…5bef
0x34b655…2a6f
4 touches
1 conflict
0x3027f5b0…7a3f
0x34b655…2a6f
4 touches
1 conflict
0x32e1d03e…68a7
0x34b655…2a6f
4 touches
1 conflict
0x673a703c…6433
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
3 conflicts on slot 0x19cb4cde58…72bfd9
Audit this contract →
← previous block·next block →recent activity