← previous blocknext block →recent activity
Analyzing
Block #101,492,489
13 transactions · 10 stateful · 2026-09-03 02:14:27 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,492,489 · 13 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
2w03w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dffc33e…068d
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0x019aad94…9d0e
0x34b655…2a6f
2 touches
0 conflicts
0x1d6e9b1e…1c8c
0x34b655…2a6f
2 touches
0 conflicts
0x21e8ab54…3b4b
0x34b655…2a6f
2 touches
0 conflicts
0x261cbea7…e35d
0x34b655…2a6f
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
1 conflict on slot 0x4dffc33e8c…39068d
Audit this contract →
← previous block·next block →recent activity